Search Results

This standard defines a general-purpose Application/Executive (APEX) software interface between the Operating System of an avionics computer and the application software. The interface requirements between the application software and operating system services are defined in a manner that enables the application software to control the scheduling, communication, and status of internal processing elements. Supplement 5 adds multicore processor service capabilities.

ARINC 600 is a mechanical packaging standard that is used with the ARINC 700-series of digital avionics equipment. It provides mechanical, electrical, and environmental interfaces between LRUs and the racks or cabinets in which they are installed. Provides connector shell definition, connector insert layout and mounting dimensions.

This standard provides general and specific guidance for the development of a Portable Data Loader (PDL) for carry-on application and an Airborne Data Loader (ADL) for on-board the airplane. It specifies use of a 3.5 inch floppy disk to upload and download of data and operational programs using an ARINC 429 data bus connected to avionics computers.

This standard defines data loading equipment intended for new generation avionics equipment with high-speed Ethernet interfaces. It defines a PDL for carry-on applications and an ADL for installation on the airplane. Specific mass storage media include 3.5 inch floppy disk and CD-ROM/DVD.

This document provides an overview of the entire set of documents collectively referred to as ARINC 653. As this set of documents evolves, Supplements to Parts 1 through 5 will be made more consistent with Part 0 in conjunction with the technical changes expected to be made in the evolution of ARINC 653. A summary of the ARINC 653 documents follows: Part 0 - Overview of ARINC 653, Part 1 - Required Services, Part 2 - Extended Services, Part 3 - Conformity Test Specification, Part 4 - Subset Services, and Part 5 - Core Software Required Capabilities. Supplement 1 reflects the introduction of multicore processor support in Parts 1 and 2.

The purpose of this document is to facilitate an understanding of aircraft information security and to develop aircraft information security operational concepts. This common understanding is important since a number of subcommittees and working groups within the aeronautical industry are considering aircraft information security. This document also provides an aircraft information security process framework relating to airline operational needs that, when implemented by an airline and its suppliers, will enable the safe and secure dispatch of the aircraft in a timely manner. This framework facilitates development of cost-effective aircraft information security and provides a common language for understanding security needs.

This specification describes the features and functionality desired of a communications link using Internet Protocols (IP) to provide services between a parked aircraft and the ground IP network infrastructure. This wireless communication link, commonly referred to as Gatelink, provides a connection between the airport and the on-board aircraft network. Gatelink will enable airlines to communicate in a secure manner with the aircraft network and appliances.

This document defines a Controller Area Network (CAN) interface for current and future commercial aircraft applications. The latest version, Supplement 4, expands the document to include CAN Flexible Data rate also known as CAN FD. CAN FD has the potential to provide 4 Mbps of data transfer. Supplement 4 also introduces four new appendices on the topics of: ARINC 825 Compliance, Configuration of Bit Timing, Management Information Base (MIB) Counters, and CAN Bus Security Considerations.

This standard defines the air transport industry's standards for the transfer of digital data between avionics system elements. Part 2 provides the formats of data words with discrete bit encoding.

ARINC 429 is the most widely used data transfer method used in aviation. This document provides the standard formats for data parameters and status words transferred between avionic systems. It specifies the physical data bus, electrical characteristics, and data formats. Supplement is 19 is a routine update that defines new ARINC 429 data words, new labels, new equipment IDs, and new System Address Labels (SAL).

This standard describes the 724B version of the airborne components of ACARS, and is intended for use in conjunction with VHF radio equipment existing on the plane. This ACARS enhancement improves the ability of the system to provide air-to-ground and ground-to-air data communications.

This standard describes the technical characteristics of several digital transmission systems widely used in first-generation digital avionics. These digital transmission systems have been specified for inter-unit and inter-systems communications on board transport aircraft.

This document provides airlines, airframe manufacturers, aircraft equipment suppliers, and others with information that is specific to data, software, and ground tools used in aviation configuration and data management. As a starting point, this document provides guidance on: Which standard to use in specific situations The use of and how integrity checks should be applied Common terminology in airborne software management Since airplanes started using software controlled hardware, there has been a need to standardize processes and terminology. This document is the centroid to which other software standards are related.

This document describes effective methods to manage and distribute operation flight software programs, aeronautical data bases and other forms of software used within an airline organization. Topics include software acquisition, software receiving, software distribution and necessary documentation. The FLS management process described in ARINC 667 is compatible with published FAA/EASA guidance on this subject. Software suppliers, airline users and regulators will find this document to be a practical and effective guide.

ARINC 661 defines logical interfaces to Cockpit Display Systems (CDS) used in all types of aircraft installations. The CDS provides graphical and interactive services to user applications within the flight deck environment. When combined with data from user applications, it displays graphical images to the flight deck crew. The document emphasizes the need for independence between aircraft systems and the CDS. This document defines the interface between the avionics equipment and display system graphics generators. This document does not specify the "look and feel" of any graphical information, and as such does not address human factors issues. These are defined by the airline flight operations community. Supplement 8 adds numerous changes and additions. Eleven new widgets are added, all related to 3D Maps. Seven new widget extensions. Metadata definitions (XML) for all widgets, extensions, events, symbols, and associated data types.

The purpose of this document is to delineate, in an organized fashion, the protocols used by Aircraft Communication Addressing and Reporting System (ACARS) Management Units (MU) defined in ARINC Characteristic 724B and Communications Management Unit (CMU) defined in ARINC Characteristic 758, in their interactions with other onboard avionics equipment. The purpose of this document is to delineate, in an organized fashion, the protocols used by Aircraft Communication Addressing and Reporting System (ACARS) Management Units (MU) defined in ARINC Characteristic 724B and Communications Management Unit (CMU) defined in ARINC Characteristic 758, in their interactions with other onboard avionics equipment.